Skip to content

Conversation

@dailinsubjam
Copy link
Collaborator

@dailinsubjam dailinsubjam commented Jun 30, 2025

Closes https://app.asana.com/1/1208976916964769/project/1209392461754458/task/1210651926603246?focus=true

This PR:

  • Add an activation timestamp config.
  • Update the code so that the integration with espresso take place after the timestamp.
  • Add a test Test_EspressoCeloIntegrationActivation to test the activation. But it's flaky, and I'm adding some fixes.

Notes:

There are two ways to use Espresso, one is to enable UseEspresso to force the use, the other is to set the timestamp and it will be activated automatically after the timestamp.

This PR does not:

  • Include any consideration when running the batcher inside enclave
  • Include any contract deployment related migration
  • Test anything in devnet / testnet / real deployment
  • Care about automatic caff node activation

Key places to review:

All changes related to EspressoCeloIntegrationTime


@dailinsubjam dailinsubjam marked this pull request as draft June 30, 2025 05:59
@dailinsubjam dailinsubjam marked this pull request as ready for review July 2, 2025 05:16
@dailinsubjam dailinsubjam marked this pull request as draft July 10, 2025 17:50
@dailinsubjam
Copy link
Collaborator Author

Close in favor of the new plan Comment by Sishan Long on TP1.1 Migrate from Celo to Espresso locally ?

@dailinsubjam
Copy link
Collaborator Author

Relevant PR on adding timestamp for op-node: #200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants